Asset Information Requirements (AIR) Checklist
1. Getting Started
- Create New project: "Southbank Business Park" + import AIR template document
- Strategic Purpose: Understand Organizational Information Requirements (OIR) Goals (using the OIR template)
- Identify Maintainable Assets: (list the top assets - linked to operational goals - that will need ongoing operation, servicing, maintenance or compliance)
- Define Key Information Fields: (for each asset, clarify why/what data matters - e.g., for energy tracking, warranty claims, inspection cycles, serial number, power rating, install date)
Why this matters: Tools that support structured AIR workflows help unify scope, documentation, and deliverables into a single process. This enables traceability, better version control, and smoother handover.
2. Creating the AIR (in Scope)
- Create Assets (manually or from templates/bSDD)
- Import CSV Asset Information Requirements:
- Import Asset list
- Import Information Requirements
- Setup Information Fields
- Complete Requirements: (use AI to enrich, standardize, and for validation rules)
- Model-based Info, Descriptions, Checklists, Documents, Links, etc.
- Export IDS and Import IDS: Generating an IDS provides a machine-readable, standardized way to communicate asset information requirements - making them easier to deliver and verify.
Why this matters: Combining manual input, AI assistance, templates, and standards-based imports helps build structured AIRs with greater consistency, flexibility, and alignment to ISO 19650 processes.
3. AIR as a Contract (with Work Packages)
- Assign responsibilities to tasks and group into Work Packages
- Export contract-ready documentation with cover page, contents, and hyperlink navigation
- Enable digital agreement workflows with e-sign approvals
Why this matters: Turning requirements into contract-ready deliverables makes responsibilities clear, improves accountability, and sets shared expectations between all parties.
4. AIR Quality Tracking + COBie Handover
- Upload and manage documents against each information requirement (e.g. certificates, drawings, manuals)
- Track conditions of satisfaction using structured checklists
- Automatically validate models and deliverables against defined AIRs
- Filter data from models and export in COBie format
Why this matters: Connecting asset requirements, documentation, models, and validation in one environment streamlines review processes and ensures owners receive complete, verified handover data.
5. Recap
- A Complete and Structured AIR Workflow
- How to start from Excel, IDS, Templates and use AI
- How to create Work Packages + eSigned Contracts
- How to manage Progress Tracking + Auto-Check Models
- How to automate Handover Data
Why this matters: A structured, repeatable AIR workflow supports better collaboration, clearer expectations, and more reliable project closeout - reducing delays and rework during handover.